Tokens
Tokens are references to variable system field values. When added to printed forms, emails, or text messages, these tokens are replaced with the appropriate values when the form or email is generated. For example, specifying the **PROPERTYNAME** token in an email message would cause the actual Property Name to be substituted for the token in the email that is sent out. Tokens can be combined with static text to create customized messages.
Some tokens can be translated, as designated by the "_LANG" suffix at the end of their token name. When using these tokens, a replacement is made for the token using the appropriate language, either the user's selected language for print tokens or the default property language for email tokens.
Translated tokens are not available for all fields. You cannot create a translated token by adding _LANG to the end of an existing print or email token if a language-translated token is not defined. For a list of the available language-translated tokens, see the attached files.
Print and email tokens are added periodically as system updates are made. The most recent list can be viewed by clicking one of the links below. It contains the following information about each token:
-
Module – The main module the token is associated with.
-
Field – The name of the user interface field that the token corresponds to.
-
Field Note – Any important information you should know about using the token.
-
Print Token – The token as it is used in printed forms. Print tokens are usually surrounded by ** characters.
-
Language Print Token – The translatable print token, if available.
-
Email Token – The token as it is used in emails or text messages. Email tokens are usually surrounded by %% characters.
-
Language Email Token – The translatable email token, if available.
To open a list of the available tokens as either an Excel spreadsheet or a static PDF file, click one of the following links.
